Drop support for Flink 1.17, 1.18 and 1.19 - #7633
Closed
pan3793 wants to merge 2 commits into
Closed
Conversation
### Why are the changes needed? Flink 1.17, 1.18 and 1.19 are EOL and were deprecated earlier (KYUUBI apache#7199, KYUUBI apache#7285), with their building support already removed. Kyuubi 1.13 drops the remaining support, making Flink 1.20 the minimum. Flink 2.0 is EOL, so it is marked deprecated. ### What changes are proposed? - Remove the flink-1.17/flink-1.18/flink-1.19 Maven profiles and their deprecation warning - Drop Flink 1.17/1.18/1.19 from the CI matrix - Clean up stale adaptation code that only existed for Flink < 1.20, including the FlinkResultSet reflection shim, the 4-arg DefaultContext.load branch, and >= "1.17" test guards - Deprecate Flink 2.0 at engine startup - Update docs to record the removal and deprecation ### How was this patch tested? Cross-version tested: engine compiled with Flink 1.20, run against a Flink 2.3.0 distribution; FlinkOperationSuite and FlinkOperationSuiteOnYarn passed 12/12. CI coverage: the flink-it matrix keeps Flink 1.20 (JDK 8) plus Flink 2.0/2.1/2.2/2.3 binary verification (JDK 17). Spotless and Scalastyle pass. ### Was this patch authored or co-authored using generative AI tooling? Assisted-by: DeepSeek V4 Pro
wForget
approved these changes
Aug 14, 2026
FLINK-35525 (1.20.0) allows the kyuubi delegation token provider to pass tokens to the YARN AM, and Flink 1.20 is now the minimum supported version, so the temporary HADOOP_TOKEN_FILE workaround is no longer needed.
Member
Author
|
thanks, merged to master |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are the changes needed?
Flink 1.17, 1.18 and 1.19 are EOL and were deprecated earlier (KYUUBI #7199, KYUUBI #7285),
with their building support already removed. Kyuubi 1.13 drops the remaining support, making
Flink 1.20 the minimum. Flink 2.0 is EOL, so it is marked deprecated.
What changes are proposed?
FlinkResultSet reflection shim, the 4-arg DefaultContext.load branch, and >= "1.17" test guards
FLINK-35525 (1.20.0)
How was this patch tested?
Cross-version tested: engine compiled with Flink 1.20, run against a Flink 2.3.0 distribution;
FlinkOperationSuite and FlinkOperationSuiteOnYarn passed 12/12.
CI coverage: the flink-it matrix keeps Flink 1.20 (JDK 8) plus Flink 2.0/2.1/2.2/2.3
binary verification (JDK 17). Spotless and Scalastyle pass.
Was this patch authored or co-authored using generative AI tooling?
Assisted-by: DeepSeek V4 Pro